Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic import from Blogger export #1390

Closed
wants to merge 2 commits into from
Closed

Conversation

jml
Copy link
Contributor

@jml jml commented Jul 5, 2014

It's possible to export an entire Blogger blog into a single Atom XML.

The 'feed' importer does a pretty good job at this, but it gets a few things wrong:

  • comments & settings show up as posts
  • slug doesn't match the blogger slug
  • it encodes the 'kind' as just another tag
  • it doesn't identify pages

This importer addresses those issues.

It doesn't try to clean up Blogger's (usually awful) HTML.

I had the best results running it with --wp-custpost (to separate out settings, templates, and comments) and --dir-page, like this:

pelican-import --blogger -m markdown -o $OUTPUT_DIR --wp-custpost --dir-page blog-08-29-2013.xml

At least on my blog, the generated rST is useless.

Review on Reviewable

jml added 2 commits July 5, 2014 11:10
Handles blogger input in exactly the same way as any Atom feed
- Sorts entries into correct 'kinds'
- Uses link for slug for posts (for closer URL matching)
- Relies on '--wp-custpost'
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.48%) when pulling 9c0e077 on jml:blogger-import into 8d14872 on getpelican:master.

@shrayasr
Copy link
Contributor

Just tried this out for importing my blogger blog. 👍 from me. Thanks man!

@jml
Copy link
Contributor Author

jml commented Sep 3, 2015

There's been no movement on this for a while. I'm going to close it so it's not cluttering up my pulls page. Feel free to use the code.

@jml jml closed this Sep 3, 2015
@justinmayer
Copy link
Member

Very sorry about that, Jonathan. Rest assured we'll incorporate your enhancement when we migrate the import function to the separate Pelican Tools repository. Thanks for your patience and understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants